Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create PFB-based verbatim manifest format for AnVIL (#6040) #6115

Merged
merged 11 commits into from
Apr 24, 2024

Conversation

nadove-ucsc
Copy link
Contributor

@nadove-ucsc nadove-ucsc commented Apr 2, 2024

Connected issues: #6040

Checklist

Author

  • PR is a draft
  • Target branch is develop
  • Name of PR branch matches issues/<GitHub handle of author>/<issue#>-<slug>
  • On ZenHub, PR is connected to all issues it (partially) resolves
  • PR description links to connected issues
  • PR title matches1 that of a connected issue or comment in PR explains why they're different
  • PR title references all connected issues
  • For each connected issue, there is at least one commit whose title references that issue

1 when the issue title describes a problem, the corresponding PR
title is Fix: followed by the issue title

Author (partiality)

  • Added p tag to titles of partial commits
  • This PR is labeled partial or completely resolves all connected issues
  • This PR partially resolves each of the connected issues or does not have the partial label

Author (chains)

  • This PR is blocked by previous PR in the chain or is not chained to another PR
  • The blocking PR is labeled base or this PR is not chained to another PR
  • This PR is labeled chained or is not chained to another PR

Author (reindex, API changes)

  • Added r tag to commit title or the changes introduced by this PR will not require reindexing of any deployment
  • This PR is labeled reindex:dev or the changes introduced by it will not require reindexing of dev
  • This PR is labeled reindex:anvildev or the changes introduced by it will not require reindexing of anvildev
  • This PR is labeled reindex:anvilprod or the changes introduced by it will not require reindexing of anvilprod
  • This PR is labeled reindex:prod or the changes introduced by it will not require reindexing of prod
  • This PR is labeled reindex:partial and its description documents the specific reindexing procedure for dev, anvildev, anvilprod and prod or requires a full reindex or carries none of the labels reindex:dev, reindex:anvildev, reindex:anvilprod and reindex:prod
  • This PR and its connected issues are labeled API or this PR does not modify a REST API
  • Added a (A) tag to commit title for backwards (in)compatible changes or this PR does not modify a REST API
  • Updated REST API version number in app.py or this PR does not modify a REST API

Author (upgrading deployments)

  • Ran make image_manifests.json and committed the resulting changes or this PR does not modify azul_docker_images, or any other variables referenced in the definition of that variable
  • Documented upgrading of deployments in UPGRADING.rst or this PR does not require upgrading deployments
  • Added u tag to commit title or this PR does not require upgrading deployments
  • This PR is labeled upgrade or does not require upgrading deployments
  • This PR is labeled deploy:shared or does not modify image_manifests.json, and does not require deploying the shared component for any other reason
  • This PR is labeled deploy:gitlab or does not require deploying the gitlab component
  • This PR is labeled deploy:runner or does not require deploying the runner image

Author (hotfixes)

  • Added F tag to main commit title or this PR does not include permanent fix for a temporary hotfix
  • Reverted the temporary hotfixes for any connected issues or the none of the stable branches (anvilprod and prod) have temporary hotfixes for any of the issues connected to this PR

Author (before every review)

  • Rebased PR branch on develop, squashed old fixups
  • Ran make requirements_update or this PR does not modify requirements*.txt, common.mk, Makefile and Dockerfile
  • Added R tag to commit title or this PR does not modify requirements*.txt
  • This PR is labeled reqs or does not modify requirements*.txt
  • make integration_test passes in personal deployment or this PR does not modify functionality that could affect the IT outcome

Peer reviewer (after approval)

  • PR is not a draft
  • Ticket is in Review requested column
  • PR is awaiting requested review from system administrator
  • PR is assigned to only the system administrator

System administrator (after approval)

  • Actually approved the PR
  • Labeled connected issues as demo or no demo
  • Commented on connected issues about demo expectations or all connected issues are labeled no demo
  • Decided if PR can be labeled no sandbox
  • A comment to this PR details the completed security design review
  • PR title is appropriate as title of merge commit
  • N reviews label is accurate
  • Moved ticket to Approved column
  • PR is assigned to only the operator

Operator (before pushing merge the commit)

  • Checked reindex:… labels and r commit title tag
  • Checked that demo expectations are clear or all connected issues are labeled no demo
  • Squashed PR branch and rebased onto develop
  • Sanity-checked history
  • Pushed PR branch to GitHub
  • Ran _select dev.shared && CI_COMMIT_REF_NAME=develop make -C terraform/shared apply_keep_unused or this PR is not labeled deploy:shared
  • Ran _select dev.gitlab && CI_COMMIT_REF_NAME=develop make -C terraform/gitlab apply or this PR is not labeled deploy:gitlab
  • Ran _select anvildev.shared && CI_COMMIT_REF_NAME=develop make -C terraform/shared apply_keep_unused or this PR is not labeled deploy:shared
  • Ran _select anvildev.gitlab && CI_COMMIT_REF_NAME=develop make -C terraform/gitlab apply or this PR is not labeled deploy:gitlab
  • Checked the items in the next section or this PR is labeled deploy:gitlab
  • PR is assigned to only the system administrator or this PR is not labeled deploy:gitlab

System administrator

  • Background migrations for dev.gitlab are complete or this PR is not labeled deploy:gitlab
  • Background migrations for anvildev.gitlab are complete or this PR is not labeled deploy:gitlab
  • PR is assigned to only the operator

Operator (before pushing merge the commit)

  • Ran _select dev.gitlab && make -C terraform/gitlab/runner or this PR is not labeled deploy:runner
  • Ran _select anvildev.gitlab && make -C terraform/gitlab/runner or this PR is not labeled deploy:runner
  • Added sandbox label or PR is labeled no sandbox
  • Pushed PR branch to GitLab dev or PR is labeled no sandbox
  • Pushed PR branch to GitLab anvildev or PR is labeled no sandbox
  • Build passes in sandbox deployment or PR is labeled no sandbox
  • Build passes in anvilbox deployment or PR is labeled no sandbox
  • Reviewed build logs for anomalies in sandbox deployment or PR is labeled no sandbox
  • Reviewed build logs for anomalies in anvilbox deployment or PR is labeled no sandbox
  • Deleted unreferenced indices in sandbox or this PR does not remove catalogs or otherwise causes unreferenced indices in dev
  • Deleted unreferenced indices in anvilbox or this PR does not remove catalogs or otherwise causes unreferenced indices in anvildev
  • Started reindex in sandbox or this PR is not labeled reindex:dev
  • Started reindex in anvilbox or this PR is not labeled reindex:anvildev
  • Checked for failures in sandbox or this PR is not labeled reindex:dev
  • Checked for failures in anvilbox or this PR is not labeled reindex:anvildev
  • The title of the merge commit starts with the title of this PR
  • Added PR # reference to merge commit title
  • Collected commit title tags in merge commit title but only included p if the PR is also labeled partial
  • Moved connected issues to Merged column in ZenHub
  • Pushed merge commit to GitHub

Operator (chain shortening)

  • Changed the target branch of the blocked PR to develop or this PR is not labeled base
  • Removed the chained label from the blocked PR or this PR is not labeled base
  • Removed the blocking relationship from the blocked PR or this PR is not labeled base
  • Removed the base label from this PR or this PR is not labeled base

Operator (after pushing the merge commit)

  • Pushed merge commit to GitLab dev
  • Pushed merge commit to GitLab anvildev
  • Build passes on GitLab dev
  • Reviewed build logs for anomalies on GitLab dev
  • Build passes on GitLab anvildev
  • Reviewed build logs for anomalies on GitLab anvildev
  • Ran _select dev.shared && make -C terraform/shared apply or this PR is not labeled deploy:shared
  • Ran _select anvildev.shared && make -C terraform/shared apply or this PR is not labeled deploy:shared
  • Deleted PR branch from GitHub
  • Deleted PR branch from GitLab dev
  • Deleted PR branch from GitLab anvildev

Operator (reindex)

  • Deindexed all unreferenced catalogs in dev or this PR is neither labeled reindex:partial nor reindex:dev
  • Deindexed all unreferenced catalogs in anvildev or this PR is neither labeled reindex:partial nor reindex:anvildev
  • Deindexed specific sources in dev or this PR is neither labeled reindex:partial nor reindex:dev
  • Deindexed specific sources in anvildev or this PR is neither labeled reindex:partial nor reindex:anvildev
  • Indexed specific sources in dev or this PR is neither labeled reindex:partial nor reindex:dev
  • Indexed specific sources in anvildev or this PR is neither labeled reindex:partial nor reindex:anvildev
  • Started reindex in dev or this PR does not require reindexing dev
  • Started reindex in anvildev or this PR does not require reindexing anvildev
  • Checked for, triaged and possibly requeued messages in both fail queues in dev or this PR does not require reindexing dev
  • Checked for, triaged and possibly requeued messages in both fail queues in anvildev or this PR does not require reindexing anvildev
  • Emptied fail queues in dev or this PR does not require reindexing dev
  • Emptied fail queues in anvildev or this PR does not require reindexing anvildev

Operator

  • Propagated the deploy:shared, deploy:gitlab, deploy:runner, reindex:partial, reindex:anvilprod and reindex:prod labels to the next promotion PRs or this PR carries none of these labels
  • Propagated any specific instructions related to the deploy:shared, deploy:gitlab, deploy:runner, reindex:partial, reindex:anvilprod and reindex:prod labels, from the description of this PR to that of the next promotion PRs or this PR carries none of these labels
  • PR is assigned to no one

Shorthand for review comments

  • L line is too long
  • W line wrapping is wrong
  • Q bad quotes
  • F other formatting problem

@nadove-ucsc nadove-ucsc added API API change affecting callers chained [process] PR needs to based of develop before merging labels Apr 2, 2024
@github-actions github-actions bot added the orange [process] Done by the Azul team label Apr 2, 2024
@nadove-ucsc nadove-ucsc force-pushed the issues/nadove-ucsc/6040-pfb-verbatim-manifest branch 2 times, most recently from 2c2b945 to a6aafd1 Compare April 2, 2024 02:39
Copy link

codecov bot commented Apr 2, 2024

Codecov Report

Attention: Patch coverage is 88.34356% with 19 lines in your changes are missing coverage. Please review.

Project coverage is 85.39%. Comparing base (9149d91) to head (8cb87e9).

Files Patch % Lines
test/integration_test.py 0.00% 16 Missing ⚠️
src/azul/service/avro_pfb.py 95.65% 3 Missing ⚠️
Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #6115      +/-   ##
===========================================
+ Coverage    85.36%   85.39%   +0.03%     
===========================================
  Files          154      154              
  Lines        20170    20290     +120     
===========================================
+ Hits         17218    17327     +109     
- Misses        2952     2963      +11     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@dsotirho-ucsc dsotirho-ucsc changed the base branch from issues/nadove-ucsc/6028-create-verbatim-jsonl to develop April 2, 2024 19:56
@dsotirho-ucsc dsotirho-ucsc removed the chained [process] PR needs to based of develop before merging label Apr 2, 2024
@nadove-ucsc nadove-ucsc force-pushed the issues/nadove-ucsc/6040-pfb-verbatim-manifest branch 2 times, most recently from d6997d8 to bcc89d6 Compare April 4, 2024 04:33
@coveralls
Copy link

coveralls commented Apr 4, 2024

Coverage Status

Changes unknown
when pulling 8cb87e9 on issues/nadove-ucsc/6040-pfb-verbatim-manifest
into ** on develop**.

@nadove-ucsc nadove-ucsc force-pushed the issues/nadove-ucsc/6040-pfb-verbatim-manifest branch 9 times, most recently from 76fd8a6 to 0a78b85 Compare April 12, 2024 01:59
@nadove-ucsc
Copy link
Contributor Author

  • Integration tests pass on personal deployments colocated with dev, anvildev, and anvilprod.

  • Tested successful handover of verbatim PFB manifest on personal deployment colocated with anvildev (workspace link and anvilprod (workspace link).

  • Generation of unfiltered manifest fails on personal deployment colocated with dev due to an inconsistency in the shape of the contents.contributors.project_role field for project replicas. Some projects use the form:

"project_role" : {
    "ontology_label" : "experimental scientist",
    "text" : "experimental scientist",
    "ontology" : "EFO:0009741"
}

But others have

"project_role" : "experimental scientist"

To fix this, we could make the schema parsing more flexible by just using a union whenever we encounter a polymorphic field like this.

@nadove-ucsc nadove-ucsc force-pushed the issues/nadove-ucsc/6040-pfb-verbatim-manifest branch 2 times, most recently from ae149dc to 8495197 Compare April 12, 2024 20:24
@nadove-ucsc nadove-ucsc added the WIP [process] Work in progress label Apr 12, 2024
@nadove-ucsc nadove-ucsc force-pushed the issues/nadove-ucsc/6040-pfb-verbatim-manifest branch from 3ca0110 to 8495197 Compare April 12, 2024 23:40
@nadove-ucsc nadove-ucsc added the base [process] Another PR needs to be rebased before merging this one label Apr 12, 2024
@@ -89,6 +90,10 @@ class CannedFileTestCase(AzulUnitTestCase):
expected outputs.
"""

@classmethod
def _data_path(cls, module: Literal['service', 'indexer'], path: str) -> str | bytes:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

L and I prefer using Path instances over raw strings to represent file paths

response = self._get_manifest(ManifestFormat.verbatim_jsonl, filters={})
self.assertEqual(200, response.status_code)
manifest = [
json.loads(row)['contents']
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should assert the entire row, i.e., the type and contents properties.

src/azul/service/avro_pfb.py Show resolved Hide resolved
@hannes-ucsc hannes-ucsc removed their assignment Apr 12, 2024
@nadove-ucsc nadove-ucsc force-pushed the issues/nadove-ucsc/6040-pfb-verbatim-manifest branch from 8495197 to 309aa17 Compare April 13, 2024 00:25
Copy link
Member

@hannes-ucsc hannes-ucsc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@hannes-ucsc hannes-ucsc removed their assignment Apr 22, 2024
@nadove-ucsc nadove-ucsc force-pushed the issues/nadove-ucsc/6040-pfb-verbatim-manifest branch from 5c6fe2a to 5199c21 Compare April 22, 2024 08:22
@hannes-ucsc hannes-ucsc force-pushed the issues/nadove-ucsc/6040-pfb-verbatim-manifest branch from 99ce91e to 8cb87e9 Compare April 24, 2024 18:16
@hannes-ucsc
Copy link
Member

Security design review

  • Security design review completed; this PR does not
    • … affect authentication; for example:
      • OAuth 2.0 with the application (API or Swagger UI)
      • Authentication of developers with Google Cloud APIs
      • Authentication of developers with AWS APIs
      • Authentication with a GitLab instance in the system
      • Password and 2FA authentication with GitHub
      • API access token authentication with GitHub
      • Authentication with Terra
    • … affect the permissions of internal users like access to
      • Cloud resources on AWS and GCP
      • GitLab repositories, projects and groups, administration
      • an EC2 instance via SSH
      • GitHub issues, pull requests, commits, commit statuses, wikis, repositories, organizations
    • … affect the permissions of external users like access to
      • TDR snapshots
    • … affect permissions of service or bot accounts
      • Cloud resources on AWS and GCP
    • … affect audit logging in the system, like
      • adding, removing or changing a log message that represents an auditable event
      • changing the routing of log messages through the system
    • … affect monitoring of the system
    • … introduce a new software dependency like
      • Python packages on PYPI
      • Command-line utilities
      • Docker images
      • Terraform providers
    • … add an interface that exposes sensitive or confidential data at the security boundary
    • … affect the encryption of data at rest
    • … require persistence of sensitive or confidential data that might require encryption at rest
    • … require unencrypted transmission of data within the security boundary
    • … affect the network security layer; for example by
      • modifying, adding or removing firewall rules
      • modifying, adding or removing security groups
      • changing or adding a port a service, proxy or load balancer listens on
  • Documentation on any unchecked boxes is provided in comments below

@achave11-ucsc achave11-ucsc added the sandbox [process] Resolution is being verified in sandbox deployment label Apr 24, 2024
@achave11-ucsc achave11-ucsc merged commit 1794c26 into develop Apr 24, 2024
11 checks passed
@achave11-ucsc achave11-ucsc removed the base [process] Another PR needs to be rebased before merging this one label Apr 24, 2024
@achave11-ucsc achave11-ucsc deleted the issues/nadove-ucsc/6040-pfb-verbatim-manifest branch April 24, 2024 23:13
@achave11-ucsc achave11-ucsc removed their assignment Apr 24, 2024
@achave11-ucsc achave11-ucsc restored the issues/nadove-ucsc/6040-pfb-verbatim-manifest branch April 24, 2024 23:17
@achave11-ucsc achave11-ucsc deleted the issues/nadove-ucsc/6040-pfb-verbatim-manifest branch April 24, 2024 23:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2 reviews [process] Lead requested changes twice API API change affecting callers orange [process] Done by the Azul team sandbox [process] Resolution is being verified in sandbox deployment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants